home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
BBS Toolkit
/
BBS Toolkit.iso
/
doors_1
/
mmdemo.zip
/
MM-MULT.ZIP
/
UPGRADE.DOC
< prev
Wrap
Text File
|
1992-07-04
|
12KB
|
257 lines
UPGRADING TO VER 2.0 OF THE MAINMAIL SYSTEM
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
First, you MUST upgrade your Gap to version 6.0 BEFORE upgrading
your Markmail Ver 1.x to The MainMail System. DO NOT begin this
procedure until Gap Ver 6.0 is COMPLETELY upgraded and running.
The MainMail System changes many things from Markmail Ver 1.x. To
begin with, there is no conversion for your old Markmail.USR file, so
your users will have to reregister themselves and reselect their
forums through MainMail. If you followed the Gap 6.0 upgrade docs to
the letter, you have most likely already unregistered your users from
all public forums anyway. I pondered writing a conversion program,
but decided that most if not all of your pointers etc would be lost in
the Gap conversion anyway.
First, The MainMail System Ver 2.0 uses a new ISAM user file,
located in your Gap MAIN directory, named MMUSER.DAT with an
associated index named MMUSER.IDX.
Second, The MainMail System uses a new configuration file called
MMDAT.CNF. This file can, as before, be located either in your Gap
MAIN directory, or in the current directory.
Third, The MainMail System uses a new encryption scheme for the key
file, so your old MARKMAIL.SYS file is no longer valid. You MUST
obtain a passcode from The Main Shop BEFORE your MainMail door will
function properly. If you have not obtained the passcode for your
copy of MainMail, it will run as a demo until you do.
Now, on with the show......
1). Delete your MARKMAIL.SYS and MARKMAIL.USR files. They are
no longer used. Also, delete any old copies of MMSM.EXE and
MM-GAP.EXE that you still have.
2). Rename your MARKMAIL.DAT file to MMDAT.CNF. The MainMail
System will detect the older format, and update this file
the first time either the door is opened, or MMSETUP is run.
a) If you wish, you may delete MARKMAIL.DAT, and MMSETUP
will create a new one the first time it is run.
3). Copy (unzip) the EXEs to your path, or wherever you had
MM-GAP.EXE and MMSM.EXE before.
a) There are three EXEs. MM-GAP.EXE, MMSETUP.EXE and
MMPACK.EXE.
4). Copy (unzip) the new GEN dir files, (MM-MENU etc) to where
you had them before, or update your old MM-MENU file to add
the new commands. (See the MM-MENU file provided for a
summary of all available commands).
5). Copy (unzip) the HELP.ZIP files to wherever you had the old
Markmail help files. Be sure to overwrite or delete the old
ones, they have all changed!
6). Run MMSETUP.EXE and make any necessary changes, updates to
your paths, and filenames. If you wish, you may delete your
old MARKMAIL.DAT file (MMDAT.CNF) and MMSETUP will create a
new one. If you decide to do this, MMSETUP will read your
Gap setup and fill in the most common paths, protocols, and
compression methods for you. MMSETUP assumes that you are
running MainMail from your Gap default dir as an integral
part of Gap. See the documentation for more details on
running MainMail from its own directory instead.
7). FROM YOUR GAP DEFAULT DIRECTORY, run MM-GAP with the
<register> parameter. Like this:
mm-gap register <enter>
Answer the questions as they come up, and enter your
passcode obtained from The Main Shop or from your
registration letter. MainMail will create a new MMSYS.DAT
(formerly MARKMAIL.SYS) file in the current directory. Once
finished, you may copy this to your Gap MAIN directory and
MainMail will find it there for all nodes.
That's it. Your MainMail door is ready to run. MainMail
will create new MMUSER.DAT and MMUSER.IDX files the first
time the door is opened.
-------------------------------------------------------------------
Changes in The MainMail System Ver 2.00.
1) The MainMail System now writes directly to the Gap caller logs.
A list of caller log codes and their meanings is contained in
the appendixes of The MainMail docs.
2) MainMail now reads a user's default protocol from Gap when a new
user first opens the door, and if that same protocol letter is
configured in MainMail, that protocol will be the user's default
in MainMail. This should provide one less thing for the user to
have to set up in MainMail.
3) Added 'DQ', 'UQ', and 'UG' commands. These are, Download/Quit,
Upload/Quit, and Upload/Goodbye respectively. Try them.
4) MainMail will operate locally from the command line using either
of these switches:
'-U' uploads a local packet from the path configured in MMSETUP.
'-D' downlaods a local packet to the path configured in MMSETUP.
NOTE: MainMail still requires a DOOR.SYS file to be present in
the default directory when operated locally. MainMail
obtains the user's name currently in the door from
DOOR.SYS. If you intend to operate MainMail in an event
or at any time locally, you MUST have a copy of DOOR.SYS
in your Gap defualt with YOUR name in it as the user
currently logged on. I did this by creating a directory
under the default called 'dorsys' and copying DOOR.SYS
into it. Then, whenever I run MainMail locally, I do so
from a batch file, and copy that DOOR.SYS to the defualt
directory immediately before running MainMail. For
example:
MMU.BAT <Local upload batch file>
-------
@echo off
copy .\dorsys\door.sys
mm-gap -u
MMD.BAT <Local download batch file>
-------
@echo off
copy .\dorsys\door.sys
mm-gap -d
As a side benefit of this, you can accually have any
number of door.sys files in that directory, each with a
different name. This might be desirable if several people
all obtain their mail locally through MainMail. Here is
an example to how this might work:
MMD-JOHN.BAT <John Smith's Local Download batch file>
------------
@echo off
copy .\dorsys\john.sys <door.sys for John Smith renamed>
mm-gap -d
ren d:\path\idcode.qwk d:\path\john.qwk
<d:\path> would be your local download path as configured
in MMSETUP.
5) There will be a DEMO version available soon. This will
hopefully allow more potential MainMail sysops to try the door
before buying it. The demo will be FULL FEATURED, and will have
not be crippled except that it will only allow 20 users in the
user file. The QWK file name will be DEMO.QWK(REP).
Please make this demo version available to your users to
download. Thank you!
6) MainMail creates a WORK directory either under the current
directory, or off of the root of the directory specified in
MMSETUP. Previous versions of Markmail For Gap deleted this
directory when done with it. MainMail now leaves this directory
in place upon exit. This allows Novell network administrators
to flag that directory as a PURGE directory without MainMail
disturbing those attributes. This WORK directory is named
'MWORK' for single node versions, or 'MWORKxx' for multi-node
versions, where 'xx' is the node number. (01 thru 99).
7) MainMail now extracts new files and bulletins on a forum by
forum basis during the download process.
8) MainMail includes a new file in the packet called 'DOOR.ID'.
This file will inform the mail readers about the door, and help
to implement off-line configuration more easilly.
9) MainMail also includes a new pointer file in the packet. This
file, named idcode.PTR is a standard C struct and utilizes the
following format:
struct pointer
{
unsigned int forum; /* Forum number for this record */
unsigned int misc; /* For future use */
long highnum; /* High msg number for this forum */
}; /* 8 bytes per record */
Developers and Mail Readers may use this file any way they wish.
This information is provided as a courtesy for those of you who
wish to use this file.
There is one record for each forum CURRENTLY SELECTED. No
record appears if the forum in question is not selected. If a
record is added to this file, and the file uploaded in a mail
packet, MainMail will add that forum to the list of selected
forums, with flags set to ALL MAIL and set the high message
number to the number appearing in the new record.
Additionally, if an existing record is modified, IE: high number
changed, and the file is included in an uploaded packet,
MainMail will make the changes reflected in the updated record.
Some caution should be exercised when manipulating this file.
If a random or garbage number is placed in this file, and the
file is uploaded, MainMail will take the data as valid and make
the changes unconditionally. In other words, if a high number
of 60 million is placed in the record for forum 5, MainMail will
set the high number for forum 5 to 60 million.
10) MainMail deletes the REP packet when a successfull LOCAL upload
is performed. This should help to prevent those occational
infections of FHD we all have. (Ask Frank Hagan what FHD is!)
------------------------------------------------------------------
New Utilities....
MMPACK.EXE - Packs your MainMail user file. No command line
parameters are needed or accepted. This program does
nothing more than read your MMUSER.DAT file, and check
that each user exists in Gap. If a user does not
exist in Gap, s/he is deleted from the MainMail user
file. The intended purpose is to perform the accual
purge of users from Gap using GAPPACK, then run MMPACK
to 'sync' the MainMail user file to the Gap user file.
Simply add the line 'MMPACK' to your event immediately
following the GAPPACK on your user file.
MMPACK.EXE renames your MMUSER.DAT and MMUSER.IDX
files to MMOLD.* in your MAIN directory. You may
leave them there, or delete them after the pack is
complete. If you leave them there, MMPACK.EXE will
overwrite them the next time it is run. This could be
considered a safe way of always keeping a backup of
your MMUSER files.
THIS IS A SINGLE USER PROGRAM!!! ALL NODES MUST BE
SHUTDOWN BEFORE RUNNING THIS PROGRAM!!! THIS PROGRAM
MUST BE RUN FROM YOUR GAP DEFAULT DIRECTORY!!!
MMSETUP.EXE - This program replaces MMSM.EXE. All operation is
similar or identical to before. There are two major
differences.
First, in a NEW installation, (one where MMDAT.CNF
does not already exist), MMSETUP creates a new
MMDAT.CNF file with all common protocols, compression
methods and directoried already entered for you.
Should save some typing.
Second, the user file editor is now operative. You
can edit or delete existing user records from your
MainMail user file when desired. If you have the
multi-user version of MMSETUP, it can be run at the
same time the MainMail soor is running on another
node.